🏁 Script executed:

#!/bin/bash
# Find the applyPreset function implementation
ast-grep --pattern 'void applyPreset($$$) {
  $$$
}'

Length of output: 0

🏁 Script executed:

#!/bin/bash
# Search for CALL_MODE constant definitions
rg -n "^\s*#define\s+CALL_MODE" --type=cpp --type=c

Length of output: 979

🏁 Script executed:

#!/bin/bash
# Find where currentPreset is set in relation to call modes
rg -n -C5 "currentPreset\s*=" --type=cpp --type=c -g '!usermod*' | head -100

Length of output: 3921

🏁 Script executed:

#!/bin/bash
# Look for applyPreset function signature and implementation
rg -n "void applyPreset" --type=cpp --type=c -A20 | head -200

Length of output: 2716

🏁 Script executed:

#!/bin/bash
# Find the applyPreset function implementation - it seems to be inline or in presets.cpp
rg -n "^bool applyPreset" --type=cpp --type=c -A30

Length of output: 3766

🏁 Script executed:

#!/bin/bash
# Look at the stateUpdated function to understand how currentPreset gets cleared
rg -n "void stateUpdated" --type=cpp --type=c -A15

Length of output: 2150

🏁 Script executed:

#!/bin/bash
# Check how callMode affects preset application behavior
rg -n "CALL_MODE_NOTIFICATION" --type=cpp --type=c -C3 | head -80

Length of output: 6088

• File: usermod_v2_auto_playlist.h

  • Snippet: unloadPlaylist()

    • Location: lines 51-60
    • Content:

      void unloadPlaylist() {
        if (playlistEntries != nullptr) {
          delete[] playlistEntries;
          playlistEntries = nullptr;
        }
        currentPlaylist = playlistIndex = -1;
        playlistLen = playlistEntryDur = playlistOptions = 0;
        playlistSuspended = false;  // WLEDMM
        DEBUG_PRINTLN(F("Playlist unloaded."));
      }
      

    • Purpose: shows how the code unloads the current playlist and resets state before applying a new preset.

  • Snippet: changePlaylist(byte id)

    • Location: lines 84-93
    • Content:

      void changePlaylist(byte id) {
          String name = "";
          getPresetName(id, name);
          #ifdef USERMOD_AUTO_PLAYLIST_DEBUG
          USER_PRINTF("AutoPlaylist: Applying \"%s\"\n", name.c_str());
          #endif
          // if (currentPlaylist != id) {  // un-comment to only change on "real" changes
            unloadPlaylist(); // applying a preset requires to unload previous playlist
            applyPreset(id, CALL_MODE_NOTIFICATION);
          // }
          lastAutoPlaylist = id;
      }
      

    • Purpose: shows how an auto-playlist change translates into unloading the current playlist and applying a new preset via applyPreset(..., CALL_MODE_NOTIFICATION).

  • Snippet: applyPreset invocation context within changePlaylist()

    • Location: lines 90-93 (within the same snippet above)
    • Content (extracted from the snippet above):

      unloadPlaylist(); // applying a preset requires to unload previous playlist
      applyPreset(id, CALL_MODE_NOTIFICATION);
      

    • Purpose: directly demonstrates the call to applyPreset with CALL_MODE_NOTIFICATION as part of the sequence when changing to a new preset from the auto-playlist.

  • Snippet: applyPreset usage reference in loop when a new preset is selected

    • Location: within the change handling block in loop(), near where applyPreset is invoked
    • Content (reproduced from surrounding context in the file):

      // ... previously
      suspendPlaylist();
      applyPreset(newpreset, CALL_MODE_NOTIFICATION);
      // ...
      

    • Purpose: shows the explicit usage of applyPreset(newpreset, CALL_MODE_NOTIFICATION) as part of the auto-change flow, including the preceding call to suspendPlaylist(). This is relevant to evaluating whether selecting a preset should disable the auto-playlist engine.

If you need, I can summarize how these flows interact with currentPlaylist/currentPreset and the conditions that enable/disable the auto-playlist, or provide diagram-style flow descriptions based on these exact code paths.